Copyright: ® Coromandel Industries, Inc.


Help Contents
Contents

Overview

Introduction

Part I  -  Integra VDB Features and Benefits

Contents Overview

What is Integra VDB ?

Typical Database Application Architecture

Sample Database Application Development  Process

Building Address Book - the Conventional Way

Building Address Book using Integra VDB

Why Integra VDB ?

Part II - Integra VDB Components

Contents Overview

Architecture Controls

Visual Controls

Visual Query Builder

Visual  Data Manager

ODBC Interface

High Level Database Functions

Database Application Template

Summary


Introduction

This document describes Integra Visual Database Builder (VDB), a tool for building database applications using Microsoft Visual C++ or Visual Basic.  We use the common term 'visual environment' to refer to either one of these programming systems.  In case of Visual C++, the visual environment is the App Studio and Visual Workbench, whereas in case of Visual Basic, it is the Visual Basic design mode.

The document is divided into two parts.  In Part I, we describe the features and benefits of Integra VDB, along with the process of developing a database application.  In Part II, we describe Integra VDB components.


Part I  -  Integra VDB Features and Benefits - Contents Overview
Contents Overview

In this section of the document, we discuss the following topics:

•	What is Integra VDB ?

•	Typical database application architecture

•	Sample database application (Address Book) development process

•	Building Address Book - the conventional way

•	Building Address Book  using  Integra VDB

•	Why Integra VDB ?


What is Integra VDB ?

Integra VDB is a powerful tool for building Microsoft Windows-based database applications using Visual C++ or Visual Basic. It  allows rapid development by automating most of the standard database application functions.  Integra VDB applications are designed to  work with multiple Open Database Connectivity  (ODBC) drivers simultaneously.  This means that applications built using Integra VDB can be ported to several databases with virtually no additional effort.  These databases can range in power from simple dBASE type databases to powerful servers like Teradata.

Integra VDB includes the following components:

•	A set of Database Custom Controls

•	A Visual Data Manager

•	A Visual Query Builder

•	A comprehensive set of high level Database Functions written to the ODBC interface

•	Integra SQL, a powerful database engine based on the ANSI (American National Standards Institute) SQL (Structured Query Language) 92 standard. The use of this engine is optional.

In Part II, we describe these components in more detail.


Typical Database Application Architecture

We will first look at the architecture of a typical database application and the interaction between the components of this architecture.

Fig. 1 shows the components of a  typical database application.  An application consists of :

•	Forms and other visual objects

•	A set of  cursors

•	One or more connections to data sources

•	One or more data base management systems (DBMS)  that provide these data sources

•	The code that ties together these components and processes and presents data.

Fig. 1  -  Database Application Architecture

Related Topics:

Forms and Other Visual Objects

Cursors

Data Sources and Database Management Systems


Forms and Other Visual Objects

Forms (also referred to as panels or dialog boxes) act as the main interface for accepting and displaying data. A form, in turn, consists of several visual objects like text boxes, list boxes, grids, radio buttons, check boxes etc.

Buttons and  menu options, also known as command targets, can be used for  navigation between  forms. They can also be used to initiate database operations like insert, delete, update or query.  We will discuss visual objects and their mapping to database objects in greater detail in the following chapters.

Integra VDB supports several visual objects typically used in an application. It also allows you to easily map these visual  objects to database objects.


Cursors

A cursor is a database object created normally by a database query.  In this document we use the term cursor and data stream interchangeably.  Each form contains a set of visual objects bound to database fields through cursors.  A cursor may be read only or updatable.  Integra VDB supports both kinds of cursors. In addition, it also supports other types of cursors to retrieve database information and access sequential files and other file formats.


Data Sources and Database Management Systems

A data source represents a grouping of database tables.  In a SQL database management system like Integra or SQL Server, this is the same as a database. In simpler relational databases like those that support dBASE files, data source represents a set of database files.

The access to the data source is through a connection. Some database drivers allow  multiple active connections to a single data source. Others allow only one active connection to a data source.  Fig. 1 represents various possible connections.

Integra VDB does not impose any constraints on the types or number of data sources or connections in an application. It generally  reflects the capabilities of the ODBC driver for a particular database management system.


Sample Database Application Development  Process

Let us see how the components we described above interact with one another and the process by which the interaction takes place.  We will do it with a sample application consisting of a single form and a single table.

An address book is a simple database application that deals with a single table and a form.  The address book is used to maintain a list of names, addresses and phone numbers.  Let us assume that addresses and phone numbers are displayed in a form view.  The user is allowed to add, delete and change records, browse through records, and perform queries based on one or more fields. While this does not represent a typical database application, it does illustrate what a database application contains and how it is built. The address book application (called FirstApp) , when finished, will look as shown in Fig. 2.

Fig. 2  -  Illustration of Address Book Application

When you run FirstApp, it performs the following functions:

•	Connects to the data source in the sample database

•	Creates a cursor and maps it to a table

•	Opens the cursor, which in turn performs the query

•	Fetches the first record from the table

•	Maps each field in the record to the corresponding field in the form. For example, the Name field is displayed in the text box labeled Name etc.

When you select any of the buttons, say Next , the following actions take place:

•	An event is generated from the button and the database operation Fetch Next  Record is initiated.

•	If there are no more records, an exception occurs. The message

"No more records found"

is displayed in the status bar.

•	If the fetch is successful, the new record is displayed.

Let us stop here and look at the sequence of events in abstraction.

1.	An event is generated by user action (starting the application or requesting some information like Next, Prev etc.).

2.	If it is an event that requires some data access or modification, an  action on the cursor is initiated.

3.	The action on the cursor may in turn cause one or more commands to be sent through the connection to the data source.

4.	The commands to the data source are handled by the ODBC driver for that data source. The ODBC driver typically passes these commands to the underlying database management system.   Sometimes, it translates these commands to one or more commands and sends them to the data source.

5.	The database management system processes the request and returns data, status or error information.

6.	The driver passes the status or data to the application, translating this if necessary.

7.	If it passes data, the application processes the data and displays the results on the screen, performing any necessary data conversions.  If it passes status information, or error, this is conveyed to the user.


Building Address Book - the Conventional Way

A small database application like address book contains a form, a database table and some code to tie these together. To build this application  using the selected visual environment and a SQL database engine, you would need to perform the following steps:

1.	Create the table for holding phone and address information.

2.	Build a form that contains several fields (or controls in Microsoft Windows terminology) that correspond to the database fields.

3.	Write code to start the application and display the form.

4.	Write code to connect to the database.

5.	Write code to handle various events like Add, Next, Prev, Update, Delete and Query.

6.	Process  Add command

a)	Write code to accept and validate data as it is typed in the form.

b)	Write code to convert the data if needed and store it in the record buffer.

c)	Write code to  insert the record in the database.

d)	Write code to detect errors like duplicate records, if any, and display  an error message to the user.

7.	Process  Next / Previous commands

a)	Write code to read data from the table.

b)	Write code to convert the data into a proper format for display.

c)	Write code to  display an error  while moving past the beginning or end of  data.

8.	Process Query command

a)	Obtain the search criteria from the form and write code to construct a query string.

b)	Execute the query using the database engine.

c)	Read the result record and display the results in the form (write code similar to process Next).

9.	Process Update command

a)	Write code to read the forms contents.

b)	If you want to do a smart update,  write code to compare the changed record with the original record and detect the changes.

c)	Write code to generate an update statement with the changed fields.

d)	Write code to perform the update.

e)	Write code to handle any errors and display them to the user.

10.	Process Delete command

a)	Write code to generate the delete statement.

b)	Write code to perform the delete.

c)	Write code to handle any errors and display them to the user.

11.	Terminate the application

a)	Close the table or disconnect from the database.

b)	Remove the form.

As you can see, you need to write a lot of code to perform the most routine database operations. If you are using an ISAM (Indexed Sequential Access Method) database library, this will be hundreds of lines of C or Basic code. Query  processing alone will take you about a couple hundred lines of code. After all this work, your application is still specific to the database library you used and may not be portable at all.

If you are using an SQL-type programming interface (a SQL engine's native call interface or an ODBC call interface), the application will require about 400 to 500 lines of code. This is because complex query processing is taken care of by the SQL processor. It will take you many hours to get a fully functional application.

Typical database applications are more complex than the one we just discussed. They contain multiple tables and multiple forms and more complex interaction between form fields and database fields. By abstracting frequently used operations and building them as a set of reusable modules, you can reduce the amount of time you need to build these applications.


Building Address Book using Integra VDB

Integra VDB is a set of highly functional reusable modules. It takes care of  most of the tedious work and  leaves you  free to concentrate on the application logic.   Here is how you build an address book  application with Integra VDB and the visual environment:

1.	Create the table

Create the table using  the Visual Data Manager in Integra VDB.

2.	Create the form

Generate the form using the Form Builder control provided with Integra VDB.

3.	Display  form on startup

Store the list of forms in your application in an array and write less than 5 lines of code to specify the array and the number of forms in the application.  Integra VDB automatically displays the number of forms specified.

4.	Connect to the database

  	Done automatically by the code generated by Form Builder.

5.	Handle events

Done automatically by the Database Operation controls generated by the Form Builder and placed on the form.

6.	Process Add

 	Automatically performed by Integra VDB.

7.	Process Next / Previous

 	Automatically performed by Integra VDB.

8.	Process Query

Automatically performed by Integra VDB.

9.	Process Update

Automatically performed by Integra VDB.

10.	Process Delete

Automatically performed by Integra VDB.

11.	Disconnect, remove forms

Write one line of  code.

The entire application in Integra VDB requires only a few  lines of code  automatically generated by the Form Builder control and requires less than 10 minutes of your time.

With the combination of Integra VDB and the visual environment, you  reduced hours of work to minutes. How is it so easy?  Integra VDB includes custom controls that encapsulate substantial database functionality.  You simply drag and drop these controls on the form and set their properties.  In many cases, even this is done automatically by the Form Builder control.


Why Integra VDB ?

Integra VDB offers:

•	A flexible database application development environment

•	A choice of programming modes

•	Several unique features not readily found in other tools.

Related Topics:

Flexible Application Development Environment

Choice of Programming Modes

Unique Features


Flexible Application Development Environment

Integra VDB is a flexible database application development tool because it builds on powerful visual environments and helps you perform the following functions easily:

•	Generate simple or master detail  forms with visual and database controls.

•	Map visual objects to database columns. Both static mapping (invariant throughout the application) and dynamic mapping (where the mapping is changed at run time) are provided for building flexible, extensible applications.

•	Specify relationships between multiple cursors and allow your application to automatically trigger queries on one or more cursors when data is accessed from one cursor.   With Integra VDB, you can activate triggers across forms. This means that displaying data on one form would automatically change associated data on another form.

•	Map cursors to a data source.   If  the ODBC database driver allows it, your Integra VDB application can allow many cursors to be actively mapped to a single data source.

•	Move applications from one database system to another with minimum effort normally by simply changing the connection string property.

•	Access multiple data base systems simultaneously for both reading and updating.


Choice of Programming Modes

You can program with Integra VDB in three different modes.  These modes determine how much of the work you will do, and how much you will let Integra VDB do for you.

Related Topics:

Automatic Mode

Manual Mode

Mixed Mode


Automatic Mode

In this mode you write your applications with virtually no code.  You drag and drop controls on a form, set properties, define your queries using Visual Query Builder and make one or two calls to the VDB engine.


Manual Mode

In this mode you use  high level calls that are provided with Integra VDB.  You can use these calls from within your Visual C++ or Visual Basic application.   This mode is useful if you need to change the behavior of an application dynamically at run time.


Mixed Mode

This mode is a combination of the above two modes.  In this mode, you will develop an application using the automatic mode and where necessary, calls will be used to augment the application.

Generally, you will develop applications in automatic mode with  virtually no code.  In some cases, you will write code, but your applications will take less time to develop and maintain.  Regardless of which mode you adopt, your application can be ported to multiple databases.  Applications built this way also provide good performance.


Unique Features

Integra VDB offers several unique features that makes it an attractive development tool for building powerful database applications.

Feature	Benefit
Database Controls	You simply drag and drop database controls on a form to build applications with little or no code.
Form Builder Control	This control automatically generates simple or master detail forms with database buttons. Many simple applications can be built with virtually no code. Complex applications can be built quickly since the tedious form painting and property setting chores are reduced or completely eliminated.
Form Definition Control	This architecture control allows you to map visual objects in your forms to database objects and set database properties.  You can build many applications by simply dragging and dropping controls on one or more forms and defining their database properties.
Visual Query Builder	You can define and store powerful queries without any knowledge of SQL.  The Query Builder tool lets you build queries visually by selecting fields from multiple tables and simply typing the conditions in a query grid.
Support  for third party controls	Integra VDB works with several third party controls rather than replacing them with a set of database controls. You can thus choose the best mix of controls for your application.
ODBC interface	Integra VDB is designed for building sophisticated applications that will work with any database for which an ODBC driver is available. These include single tier drivers like  dBASE, Paradox or multi-tier drivers like Integra SQL, SQL Server or Oracle Server.  An SQL engine with an ODBC interface is included in the package to enable you to start building applications right out of the box.
Database Functions	Database functions integrate both visual and database operations.  You use them within your Visual C++ programs to reduce the amount of code needed for implementing Windows database applications.
Query By Forms	Integra VDB provides a facility for automatic Query By Forms.  With one statement, an application can obtain input from the user in multiple form fields, including radio buttons and check boxes, generate an SQL statement and execute it.  A user can enable/disable any field in the form from participating in the query.
Visual Data Manager	This component makes it easy to build database objects and manipulate them visually. You  can perform queries and browse the results through a spreadsheet-like table object. You can also insert, delete or update data in one or more tables.


Part II - Integra VDB Components - Contents Overview
Contents Overview

In Part II, we describe the different components of Integra VDB, which include the following:

•	Integra VDB Architecture Controls

•	Integra VDB Visual Controls

•	Visual Query Builder

•	Visual Data Manager

•	ODBC Interface

•	Integra SQL Engine

•	High Level Database Functions

•	Database Application Template.

Taken together, these components provide a powerful yet simple tool set for building sophisticated database applications.


Architecture Controls

Architecture Controls help you organize the structure of a database application and convert the visual environment into a Database Workbench.  These controls are briefly described below:

Related Topics:

Application Control - CIApp

Data Source  Control - CIDS

Query Control - CIQry

Form Builder Control - CIFrm

Form Definition Control - CIFD


Application Control - CIApp

  This control determines some global application properties like the type of error handling and the debug mode. By setting a single property, you can have errors displayed in a message box or in a text field on the form. By setting another property you can enable the trace and have SQL statements and diagnostic information dumped into a file. This control is optional. Instead of setting options as property values, you can also specify these using calls at run-time.


Data Source  Control - CIDS

  A data source control represents a connection to an ODBC data source. A single application may contain many data source controls.  The properties of this control specify how connections are established, the logical name assigned to the connection for reference by other controls, and the connection string that is sent to the ODBC driver to establish the connection.


Query Control - CIQry

  The query control can be used to specify cursor attributes.  You can use the BuildQuery property of this control to interactively build a query and generate an SQL statement for the cursor definition.

The columns or column expressions specified in the CIQry control are available to the application. Any VBX control capable of accepting input or displaying output can be bound to a column or column expression.

In addition to specifying a cursor, each CIQry can be used to define a maximum of 8 triggers. Each trigger specifies the name of another cursor and the condition that when satisfied, opens the cursor. This property allows you to specify complex cascading master-detail relationships between different tables. The master-detail relationship can be set up for multiple levels by specifying triggers for cursors at each level.

However, CIQry is not limited to building  queries and defining cursors.  You can use it to represent several other types of  data  streams listed below:

•	A  list of tables in the data source

•	A list of columns for a specified table or set of tables

•	A list of special columns for a table

•	Data type information supported by the ODBC driver

•	Import files - Delimited and dBASE-III format

•	Export files - Delimited, SDF, WKS and dBASE-III format

•	Memory files

•	Lookup files.

In addition to the above, you can also use this control to represent a generic SQL statement.


Form Builder Control - CIFrm

  The form builder control is used to generate simple and master-detail forms.  You can also customize the forms generated, by selecting different options.

The CIFrm control can be used to:

•	Generate a simple form or a master detail form

•	Specify the fields included in a form through a Visual Query Builder interface

•	Specify the type of objects to be placed on the detail form in the case of master detail form

•	Generate a form with a single column or two columns

•	Specify the caption of a form

•	Specify the combination of Browse, Query and Update database operations to be placed on a form.

The form is generated in the ASCII format.  Form Builder will prompt you to add the form to the project and upon confirmation, will add it to the project.


Form Definition Control - CIFD

 	  The form definition control is used to assign a logical name to the form. It's main purpose, however, is to bind visual controls to database columns or expressions specified in the CIQry control. In addition, it can be used to specify database properties for visual controls.

When you double click the Design property of the form definition control, it performs the following functions:

•	Scans all the active forms and the visual controls on each form

•	Scans the cursors on the active forms

•	Lets you map visual controls to columns in a cursor.

If you are mapping single-valued controls like text boxes, radio buttons and check boxes, each visual control can be mapped to a single database column or expression in the cursor.

If you are mapping multi-valued controls like list boxes, combo boxes or grids, the entire cursor must be bound  to one visual object.

A single form may contain many cursors. A form may also contain multiple visual controls like text boxes, radio buttons, list boxes, combo boxes and grids. You can set up one to many relationships between form fields and grids.


Visual Controls

There are two visual controls - CIOP and CIGrid which have special database properties. Others like text, radio button, check box, combo box etc. are provided since the visual controls available with either Visual C++ or Visual Basic do not have database properties.

Related Topics:

Database Operation Control - CIOP

Database Grid Control - CIGrid

Other Visual Controls


Database Operation Control - CIOP

  This visual control is used to specify database operations. It is similar to a button control with a set of extended properties.  The Operation property of the button control decides which database operation is initiated when the button is activated.  The Cursor Name property of the button specifies the  cursor on which the operation is performed.

The following operations are supported:

•	Clear Form

•	Clear Query Fields

•	Close Cursor

•	Delete Current Record

•	Insert Record

•	Fetch Current Record

•	Fetch Next Record

•	Fetch Previous Record

•	Fetch First Record

•	Fetch Last Record

•	Open Cursor

•	Query By Form

•	Update Record

•	Execute Chain

•	New Record.


Database Grid Control - CIGrid

 	  CIGrid is an editable grid control optimized for data access. A single form can contain multiple grids. Each grid can be tied to a cursor. You can specify the fields and the order in which fields are displayed in the grid.

When you bind data to grid columns, you can specify additional parameters like column heading, data format, alignment etc.


Other Visual Controls

In addition to the two visual controls specified above, other standard visual controls are provided. These include:

Check Box Control	CICheck
Combo Box Control	CICombo
Frame Control	CIFrame
List Box Control	CIList
Radio Button Control	CIRadio
Text Control	CIText


Visual Query Builder

Visual Query Builder (VQB) is a tool for building queries quickly and easily. With VQB you do not have to know SQL syntax or remember table or column names. You do not need to remember the join syntax for various types of database drivers. To define a query, you point and click. You must however have an understanding of how tables are organized in the database and some knowledge of how to specify expressions.

VQB  is invoked when you double click on the BuildQuery property of a CIQry control. Once you are in VQB, you can either use an existing query or define a new query.

VQB can be used to:

•	Select the tables or views for the query

•	Select one or more database fields to be included in the result table (also known as SELECT list) of a query statement

•	Specify one or more expressions to be included in the SELECT list

•	Specify JOIN conditions between multiple tables / views

•	Specify complex query criteria

•	Specify grouping and group conditions

•	Specify sort criteria for the results

•	View the generated SQL statement

•	Save the generated SQL statement in a file

•	Run the query and view the results in design mode. This helps you refine your query by "drilling down".

When more than one table is included in the query, you should specify joins between the tables. The types of joins allowed will depend on the underlying database engine. The Integra SQL engine, for example, supports Inner Join, Left Outer Join, Right Outer Join and Full Outer Join, whereas the dBASE driver supports Inner Join, Left Outer Join and Right Outer Join. To find out what types of join are supported by your database, refer to the documentation of the database management system.

With Visual Query Builder, you can specify complex query criteria that include AND, OR, BETWEEN and LIKE between multiple fields.  You can also specify that the results of the query be grouped on one or more columns or expressions.  In addition, complex criteria can be applied to groups for filtering the results of the query.

Query results can be sorted on one or more columns in ascending or descending order.  The maximum columns for other databases depends on the relevant driver.

VQB allows you to view the SQL statement generated by the query.  You can also run the query within the Query Builder, view the results and modify the query if necessary.

You can save the query in an MS-DOS file and reuse the query at a later time.

When you finish defining the query and exit VQB, the SQL statement equivalent of the query is saved in the SQLStatement property of the query control. By clicking on the SQLStatement property you can view and modify the statement.


Visual  Data Manager

The Visual  Data Manager (VDM) is a tool for creating, dropping and manipulating database objects like tables, indexes, views etc.  The capabilities may vary depending on the database driver being used.

With the Visual Data Manager for Integra SQL, you can perform the following functions:

•	Create and drop databases

•	Create and drop schema

•	Create, alter and drop tables

•	Create and drop views

•	Create and drop indexes

•	Import and export data from tables

•	Invoke Visual Query Builder to build and run queries

•	Browse tables or insert, delete and update records in a table

•	View and edit multiple tables simultaneously

•	Execute SQL commands and scripts containing SQL commands

•	Set options like current schema, date format etc.


ODBC Interface

Data access in Integra VDB is done through the ODBC interface.  Applications built with Integra VDB are designed to work with any database for which an ODBC driver is available.   A single Integra VDB application can access data from multiple database management systems.

You can also use database function calls (discussed below) as a high level programming interface that abstracts ODBC access and integrates visual and database operations.

Currently several vendors are in the process of providing ODBC drivers.  As and when drivers become available, Integra VDB will be tested with them.  For the current list of certified drivers,  please contact us or refer to the Release Notes in the Integra VDB distribution.

Integra SQL, an ODBC compliant SQL engine is tested and certified with this release of Integra VDB.

Related Topics:

Integra SQL Database Engine


Integra SQL Database Engine

The Integra SQL database engine is based on the ANSI SQL 92 standard. The native call interface is based on  ODBC which in turn is based on SQL Access Group's Call Level Interface. The database is implemented as a two tier driver. For more details on Integra SQL Database engine refer to the Integra SQL Database Interface Manual in the Integra VDB documentation set.

A single user, multi-client version of this engine is bundled with Integra VDB. The use of this engine is optional.


High Level Database Functions

In addition to database architecture controls and visual controls,  Integra VDB includes a set of database functions that enhance your ability to customize applications or fine tune the user interface.  These database functions provide a high level interface that integrate both visual and database operations.  Database functions augment the database architecture controls and both can be used in the same application.

The following functions are provided:

SQcAttachControl	Attach a control to a specified form
SQcAttachDataBase	Attach the application to a database
SQcAttachForm	Attach a form to the application
SQcBatchEdit	Update tables from memory cursor or snapshot cursor
SQcBindColumn	Bind a cursor column to user buffer
SQcBindCursor	Bind a cursor to a set of controls
SQcBindExp	Associate an expression with a visual object
SQcBindInOut	Bind visual objects to database columns
SQcBindTrigger	Associate a trigger with a cursor
SQcBuild	Build a data stream with the specified statement string
SQcBuildBindExec	Build a cursor, bind it to a set of visual objects and open the cursor to execute the statement
SQcButtonControl	Automatically enable or disable third party button controls
SQcCheckVersion	Check version number
SQcClear	Clear text boxes associated with the cursor
SQcClearForm	Clear the fields in a specified form
SQcClose	Close an open cursor
SQcCloseAndUnbind	Close an open cursor and unbind all visual objects bound to the cursor
SQcCommitWork	Make changes to the database permanent
SQcConnect	Connect the application to Integra VDB
SQcConvertToMemCursor	Convert an open cursor to a memory cursor
SQcCreateDataStream	Create a data stream
SQcDelete	Delete the current record from a cursor
SQcDeleteDataStream	Delete a data stream and release the allocated resources
SQcDeleteRecord	Delete a specified record from a cursor
SQcDetachControl	Detach a visual control from a form
SQcDetachDataBase	Detach a database from the application
SQcDetachForm	Detach an attached form
SQcDisconnect	Disconnect the application from Integra VDB
SQcExecute	Execute a list of cursors specified by name
SQcFetch	Fetch a record from the cursor
SQcFormatDate	Format date
SQcGetAppHand	Get the application handle
SQcGetColInfo	Get information about a specified column
SQcGetCursorInfo	Get information about a specified cursor
SQcGetError	Get error information
SQcGetErrorMsg	Get message string for a specified error
SQcGetHandle	Get the handle of a specified object
SQcGetLrecord	Get logical record number
SQcGetName	Get the name of a form, control or cursor
SQcGetPrecord	Get physical record number from logical record
SQcGo	Initiate actions based on controls in the loaded forms
SQcInsert	Insert a record from the attached form
SQcInsertRecord	Insert a record into the data stream from the buffer
SQcNewRecord	Append a record to the cursor with default values for all fields
SQcOpen	Open a cursor
SQcQBF	Perform a query based on form field values
SQcReadRecord	Read a specified record into the buffer
SQcReadPhysicalRecord	Read the record with a specified physical record number from the cursor into the memory buffer
SQcRollbackWork	Roll back the current transaction
SQcSetAppMode	Set application mode
SQcSetColAttr	Set column attributes
SQcSetColInfo	Set column descriptions
SQcSetCurrentForm	Make the specified form the active form
SQcSetCursorInfo	Set cursor information
SQcSetDateFormat	Specify display and driver date formats
SQcSetDBmode	Set the database access mode for the current connection
SQcSetTopRow	Set the top row of a grid
SQcTrigger	Trigger a data stream through visual object selection
SQcUnbindColumns	Unbind all columns bound to a data stream
SQcUpdate	Update record with values in the form
SQcUpdateRecord	Update specified record from the buffer
SQcVerifyHandle	Verify the data stream handle.


Database Application Template

Many database applications conform to a familiar prototype. Integra VDB provides a database application template for building and running these applications with virtually no code. Using this template you can build the following types of applications:

•	Single form applications with one table

•	Single form applications with multiple tables

•	Multi-form applications with multiple tables.

When an application contains more than one table, you can specify triggers such that fetching data from the master table automatically fetches data from detail tables. For example, when you fetch a vendor record, you can automatically fetch all the products supplied by the vendor and display them.

The database application template is provided only with the Visual C++ version of Integra VDB.  It is not needed for Visual Basic.


Summary

Integra VDB is a powerful tool for building industrial strength, portable database applications.  It is seamlessly integrated with Microsoft Visual C++ and Visual Basic to help develop sophisticated ODBC compliant database solutions easily and quickly.  Its database architecture controls and visual controls tie neatly into the selected visual environment and improve application development productivity.  Integra VDB applications are designed to work with databases that support the Open Database Connectivity standard;  in addition, an ODBC-compliant SQL database engine is built in to allow developers to develop and distribute applications right out of the box.

Related Topics:

How to Place an Order / Get More Information


How to Place an Order / Get More Information

To place an order or to get more information on Integra VDB, contact:

Coromandel Industries, Inc.

70-15 Austin Street, Third Floor

Forest Hills, NY 11375, USA.

Phone: (718) 793-7963 / (800) 535-3267

Fax: (718) 793-9710

CompuServe ID: 71531,1534

MCI Mail: Coromandel